educational

Real World Redirection

In a recent board discussion about 2257 compliance issues for overseas producers, I posted a sample of geo-redirect code that has appeared in various forms during discussions here at XBiz. The purpose of the code, implemented as part of a website's .htaccess file, is to redirect incoming website traffic to an alternate destination based upon its country of origin.

The context of 2257 in this discussion is that overseas producers and website owners who do not wish to comply with the enhanced 2257 regulations can easily block their website's availability to the US market by using a few lines of server-side coding. This is one example of the power of geo-redirects – a power which I'd like to take a closer look at today:

Separating Wheat from Chaff
Consider the flow of traffic from the Internet into your website: Depending upon your traffic sources, the percentages of the different types and origins of surfers will vary; such as US surfers coming from search engines or Bulgarians from a TGP. Inevitably, varying amounts of, to be blunt, "undesirable" surfers – and entities such as hitbots and other digital nasties – will hit your homepage.

These "undesirables" include surfers coming from countries where your products or services are illegal and surfers coming from countries with historically excessive levels of fraud, including chargebacks. As such, it behooves the website operator to immediately strip off this traffic arriving at his or her website before it even enters. Why waste bandwidth on traffic that is unprofitable and potentially dangerous?

There's no such thing as useless website traffic, however, so this undesirable traffic is not merely blocked but re-routed at the server level using the aforementioned .htaccess file. The volume of this traffic will vary from website to website, with some operators selling it directly, while others send it to sponsors or trade it for fresh surfers.

It's the latter option that I prefer. If I can trade an "undesirable" for a new surfer, then I'm happy. If I can trade one for several new surfers, then I am even happier. As such, the fate of my "undesirables" is often a "whirlwind" page where they will find top lists and trades behind every click. I'm not trying to make a buck on this visitor, I just want a shot at a better one in exchange for him.

Sometimes, filtering off foreign traffic is desirable, not because the traffic is "undesirable" – but because someone else could make better use of it than you could. For example, I can isolate, say, my Portuguese traffic and look at how well my website converts that traffic. I might also want to send that traffic to a sponsor with a Portuguese site targeting a similar niche, to measure which was the most profitable use of that particular traffic to me.

If both my own website as well as the sponsor's website were profitable to promote, then making both offers to my Portuguese surfers would be in order. I could, for example, use a full-page ad for the Portuguese website with a pass-through link to my own website – the surfer's intended destination – and send my less profitable traffic straight-through to the "whirlwind" page. Let your stats guide your actions.

You can find a list of the country codes that you'll need to build your own geo-redirect list here.

The following is an example of the geo-redirect code which you can copy and paste. It allows for separate targeting of Asian traffic with redirects to Chinese, Japanese and Korean websites, as well as a block of "high fraud" countries which redirect to a "garbage" URL – the perfect place for a "whirlwind" page:

• Asian:
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^CN$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^HK$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^MO$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^MY$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SG$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TW$ [NC]
RewriteRule ^(.*)$ https://chinese.url [R,L]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^JP$ [NC]
RewriteRule ^(.*)$ https://japanese.url [R,L]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KP$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KR$ [NC]
RewriteRule ^(.*)$ https://korean.url [R,L]

• Illegal and/or High Fraud:
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^AE$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^AF$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^AL$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^AM$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^AZ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^BG$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^BH$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^BR$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^BY$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^CR$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^CU$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^CZ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^EE$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^EG$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^GE$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^HR$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^HU$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^ID$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^IL$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^IN$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^IQ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^IR$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^JO$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KG$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KH$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KW$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^KZ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^LA$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^LB$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^LT$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^LV$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^LY$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^MD$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^OM$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^PH$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^PK$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^QA$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^RO$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^RU$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SA$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SD$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SI$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SK$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^SY$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TH$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TJ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TM$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TN$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^TR$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^UA$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^UZ$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^VN$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^YE$ [NC,OR]
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^YU$ [NC]
RewriteRule ^(.*)$ https://garbage.url [R,L]

Next week, I'll add some additional coding and put it all together for you, in "Real World .htaccess Files."

Copyright © 2025 Adnet Media. All Rights Reserved. XBIZ is a trademark of Adnet Media.
Reproduction in whole or in part in any form or medium without express written permission is prohibited.

More Articles

opinion

From Compliance Chaos to Crypto Clarity: Making the Case for Digital Payments in Adult

These are uncertain times for adult merchants. With compliance tightening and age verification mandates rising, the barrier to entry keeps getting higher.

Cathy Beardsley ·
profile

FSC's Valentine Leads Charge for Sex Worker Rights and Financial Access

Before ever stepping into a courtroom, Valentine already understood the power of presence. After all, they’ve shimmied on stages as a burlesque performer, consulted behind the scenes for creative businesses and moved through the adult industry not just as an advocate, but as a participant.

Jackie Backman ·
opinion

Breaking Down HB 805 and How it Affects the Adult Industry

North Carolina House Bill 805 was enacted July 29, after the state legislature overrode Governor Josh Stein’s veto. The provisions that relate to the adult industry, imposing requirements for age verification, consent and content removal, are scheduled to become effective Dec. 1. Platforms have until then to update their policies and systems to comply with the new regulations.

Corey D. Silverstein ·
opinion

Staying Compliant With Payment Standards Across Europe and Australia

So, you’ve got your eye on international growth. Smart move. No matter where adult-industry merchants operate, however, one requirement remains consistent: regulatory compliance. This isn’t just a legal checkbox — it’s a critical component of keeping payments flowing and business operations intact.

Jonathan Corona ·
opinion

How to Avoid Copyright Pitfalls When Using Music in Adult Content

When creating an adult video, bringing your vision to life often means assembling just the right ingredients — including the right music. However, adding music to adult content can raise complex legal and ethical issues.

Lawrence G. Walters ·
opinion

New Visa Rules Adult Merchants Need to Know

In December 2024, I shared an update on the upcoming rollout of Visa’s Acquirer Monitoring Program, also known as VAMP. The final version went into effect in June, and enforcement will begin in October. With just a month to go, now is the time to review what’s changing and how to stay compliant.

Cathy Beardsley ·
opinion

WIA Profile: Lainie Speiser

With her fiery red hair and a laugh that practically hugs you, Lainie Speiser is impossible to miss. Having repped some of adult’s biggest stars during her 30-plus years in the business, the veteran publicist is also a treasure trove of tales dating back to the days when print was king and social media not even a glimmer in the industry’s eye.

Women in Adult ·
opinion

Fighting Back Against AI-Fueled Fake Takedown Notices

The digital landscape is increasingly being shaped by artificial intelligence, and while AI offers immense potential, it’s also being weaponized. One disturbing trend that directly impacts adult businesses is AI-powered “DMCA takedown services” generating a flood of fraudulent Digital Millennium Copyright Act (DMCA) notices.

Corey D. Silverstein ·
opinion

Building Seamless Checkout Flows for High-Risk Merchants

For high-risk merchants such as adult businesses, crypto payments are no longer just a backup plan — they’re fast becoming a first choice. More and more businesses are embracing Bitcoin and other digital currencies for consumer transactions.

Jonathan Corona ·
Show More